Removal of SecureBoot options from ConfApp #432
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
impact:non-functional
github-actions
bot
added
the
impact:breaking-change
github-actions
bot
added
the
impact:non-functional
os-d
approved these changes
Feb 14, 2025
kuqin12
approved these changes
Feb 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
ConfApp's secure boot menu allows the user the illusion of being able to configure the setup boot options.
The reality is that secure boot is configured by the system prior to ConfApp, and that changes made in ConfApp are not honored on the next boot.
Removing the Secure Boot menu, associated tests and reduce the libraries needed.
How This Was Tested
CI Build.
Boot on Qemu to verify functionality.
Integration Instructions
No Changes required.